-
Notifications
You must be signed in to change notification settings - Fork 38.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
While updating NodeStatus, only first get served from cache #37788
While updating NodeStatus, only first get served from cache #37788
Conversation
lgtm |
Jenkins verification failed for commit d1ddb1fcb881c9f0145a67d0321dfb522824df47. Full PR test history. The magic incantation to run this job again is |
d1ddb1f
to
54d49cb
Compare
LGTM, but I will leave this to @lavalamp to make the final call. Thanks! |
/lgtm thanks for quick fix!! |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
Jenkins GCE etcd3 e2e failed for commit 54d49cb. Full PR test history. The magic incantation to run this job again is |
Automatic merge from submit-queue |
This PR has merge conflicts, I will not pick it up in my batch cherry pick to 1.5 branch. Please prepare a separate cherry pick. See "About Cherrypicks" section in https://groups.google.com/forum/#!topic/kubernetes-dev/mvIXrgEyHPY for help. |
@saad-ali - sure. On it. |
Ack |
…88-upstream-release-1.5 Automatic merge from submit-queue While updating NodeStatus, only first get served from cache Cherrypick #37788 to 1.5 branch.
Commit found in the "release-1.5" branch appears to be this PR. Removing the "cherrypick-candidate" label. If this is an error find help to get your PR picked. |
Fix #37725